Secure modification of controlled devices

ABSTRACT

A system and method of securely controlling a device from another device. The user of the device attempts to modify the device in some way. In response to the attempted modification a request is generated and sent to a controlling device. The request includes information related to the desired modification. The controlling device analyzes the request and a determination on how to respond to the request is made. This response is encrypted at the controlling device and transmitted to the device. The device then decrypts the response and implements the indicated response to the request. The encryption and decryption keys are burned into the corresponding devices such that information needed to decrypt the response is not transmitted to the device.

BACKGROUND

The present disclosure relates to securely controlling functions on a device from another device.

It is commonplace for individuals and organizations to control the operation and use of devices that are possessed by others. While there are many approaches that allow for one device to control the operation of another, such as multi-factor authentication, push notification or biometric validation that require the response to be entered from the controlling device, each of these approaches can be

Embodiments of the present disclosure are directed to a system and method of securely controlling a device from another device. The user of the device attempts to modify the device in some way. In response to the attempted modification a request is generated and sent to a controlling device. The request includes information related to the desired modification. The controlling device analyzes the request and a determination on how to respond to the request is made. This response is encrypted at the controlling device and transmitted to the device. The device then decrypts the response and implements the indicated response to the request. The encryption and decryption keys are burned into the corresponding devices such that information needed to decrypt the response is not transmitted to the device.

The above summary is not intended to describe each illustrated embodiment or every implementation of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings included in the present application are incorporated into, and form part of, the specification. They illustrate embodiments of the present disclosure and, along with the description, serve to explain the principles of the disclosure. The drawings are only illustrative of certain embodiments and do not limit the disclosure.

FIG. 1 is a block diagram of a system a secure communication and pairing system according to illustrative embodiments.

FIG. 2 is a flow diagram illustrating a process for creating a secure pairing between two or more devices according to illustrative embodiments.

FIG. 3 is a flow diagram illustrating a process of how the system operates during a data transfer according to illustrative embodiments.

FIG. 4 is a flow diagram illustrating a process for updating or modifying the second device according to illustrative embodiments.

FIG. 5 is a block diagram illustrating a computing system according to one embodiment.

While the invention is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the invention to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

DETAILED DESCRIPTION

Aspects of the present disclosure relate relates to secure communications and more specifically to securely controlling functions on a device from another device. While the present disclosure is not necessarily limited to such applications, various aspects of the disclosure may be appreciated through a discussion of various examples using this context.

Most devices and components are connected to each other either by wires or through wireless technologies, such as WiFi, Bluetooth, Infrared, cellular, Near Field Communications (NFC), or other wireless communications protocols. Most of these connections and links have some sort of security involved to prevent the discovery of the security keys. The downfall is that most security is implemented via software, and eventually, bugs and security holes are found. Additionally, the device operation and/or implementation is susceptible to being reverse engineered by connecting to a device and sending it commands or request and observing what the device returns. As such, the software encryption is not able to protect against reverse engineering and obtaining the encryption keys and/or the data itself.

The present disclosure burns in the encryption keys into either side of a connection or link, such that the data in each direction is both encrypted and secure. The present disclosure permanently pairs devices and/or components together. By permanently burning in encryption keys, the data is protected, and the device is useless unless paired with the original device. Bad actors attempting to reverse engineer the device are unable to communicate with the device or components, because the associated encryption is unknown and never transmitted between the two parts. Even if the encryption key is determined for one direction, the connected device is still protected with an encryption in the opposite direction.

Additionally, the present disclosure permits the controlling of activities on a device through the use of another device. Using the secure communication between the two devices, requests for use of an application or features of a device are sent to a controlling device for approval. As the communication indicating the approval/disapproval of the request is encrypted and decrypted using the present system, it becomes significantly harder for one to bypass the security controls of the controlling entity and install, use, or visit unapproved applications, features, or sites.

FIG. 1 is a block diagram illustrating a secure communication and pairing system according to embodiments of the present disclosure. System includes a first device 110 and a second device 160 that are communicatively coupled to one another such that they can send encrypted data between each other. The first device 110 includes a data processing component 105, an encryption module 120, a decryption module 130, an encryption key burner 127, a decryption key burner 137, and a communications module 140. Similarly, the second device 160 includes a data processing component 165, an encryption module 170, a decryption module 180, an encryption key burner 177, a decryption key burner 187, and a communications module 190. As the first device 110 and the second device 160 include similar components, the present discussion will discuss the various components that are similar together with reference to the first device’s components.

The first device 110 is a device that is capable of sending and receiving data to and from another device. The first device 110, can be, for example, a mobile phone, a tablet computing device, a laptop computer, a server, a gaming device, a storage device, or any other device capable of sending and receiving data. The first device 110 sends data to another device by encrypting the data that is sent to that device. Similarly, the second device 160 is a device that is capable of sending and receiving data to and from another device. The second device 160, can be, for example, a mobile phone, a laptop computer, a server, a gaming device, a storage device, or any other device capable of sending and receiving data. The second device 160 sends data to another device by encrypting the data that is sent to that device. The first device 110 and the second device 160 can be the same type of device (e.g. both are mobile phones) or can be different types of devices (e.g. a laptop computer and a server). In some embodiments, the first and second devices are discrete components within a single device. For example, the first device can be a CPU and the second device can be a memory component in the device, and the communications between the two components can be encrypted.

The data processing component 105 is a component of the first device 110 that is configured to process or generate data on the first device 110. The data processing component 105 can include, for example, one or more of, a word processing application, an email application, a data storage system, a photo processing application, an internet browser, or any other application or task that generates or manipulates data on the first device 110. Similarly, the second device 160 includes a data processing component 165 that performs similar manipulations on data. In some embodiments, the data that is generated is data that permits the updating of or modification of the second device 160. This could be useful in situations where an individual wants to control the contents or functionality of the second device 160. For example, a parent can control what is updated on the second device 160 through the use of the encryption/security of the present disclosure. Through this type of pairing of the first device 110 and the second device 160, the holder of the second device 160 would not be able to modify the second device 160 without the approval of the individual holding the first device 110.

The encryption module 120 is a component of the first device 110 that is configured to encrypt data generated or manipulated by the data processing component 105 prior to storing or transmitting the data to another device. The encryption module 120 can implement any type of encryption including symmetric and asymmetric cryptology. In some embodiments, the encryption module 120 uses public key encryption. Public key encryption uses a pair of keys, public keys which can be widely shared, and private keys which are only known by the individual who needs to decrypt the content. Some public key encryption approaches which can be employed by the encryption module 120 include, for example, Rivest-Shamir-Adleman (RSA), Diffie-Hellman, Elliptic-curve Diffie-Hellman (ECDH), Secure Remote Password Protocol (SRP), pre-shared key (PSK), Digital Signature Algorithm (DSA), Elliptic Curve DSA (ECDSA), RC4, Triple data encryption algorithm (Triple DES), Advanced Encryption Standard (AES), International Data Encryption Algorithm (IDEA), Data Encryption Standard (DES), Camellia, Hash-based MD5, and Secure Hash Algorithms (SHA) hash function. However, in some embodiments, unlike a typical public key structure, the public key used to encrypt the data is not made publicly available or otherwise openly shared with others. When data is to be transmitted from the first device 110, it is passed through the encryption module 120 which applies the encryption key and corresponding encryption algorithm to encrypt the data.

The encryption module 120 further includes a number of physically modifiable internal components 125-1, 125-2, ... 125-N (collectively PMIC 125 or PMICs 125, or PMIC 135, PMICs 135 for the decryption module 130) that holds a binary representation of the public key to be used by the encryption module 120 for encrypting the data. An encryption module 120 with a physically modifiable internal component (PMIC 125) can provide benefits over existing security techniques by ensuring that the encryption key remains secure from possible tampering or exposure. In some embodiments, the PMIC 125 is implemented using an eFuse, which is a technology for the dynamic real-time reprogramming of computer chips. eFuse has the benefit of once a “fuse” is burned, it cannot be restored to its original state. However, in some embodiments PMIC 125 can be an array of e-Fuses or EEPROM through a logic circuit, or an EEPROM gated by an e-Fuse. When gated by an e-Fuse, the gate acts as a prevention mechanism to prevent modification of the data/image located past the e-Fuse gate.

The PMIC 125 of the encryption module 120 is comprised of one or more breakable devices configured to cause an open circuit (e.g., a fuse, a wire, a conductive material with a defined brittleness). Each of the breakable devices may operate through a sacrificial operation, such as breaking. Before being broken, each breakable device is an electronic pathway through which current may flow from one end to another. Electricity can flow through continuously or in response to a request to verify the breakable device. If electricity reaches another end, the circuit is considered closed and the closed circuit may represent a value, such as a “1” or a “0”. After being broken, each breakable device is broken such that current may no longer flow from one end to another. For example, the breakable device can be constructed of a fragile nature that severs or vaporizes in response to heat, current, or other relevant cause. If electricity does not reach another end, the circuit is considered open and the open circuit may represent a value, such as a ‘0’ or a ‘1’. The value represented by an open or closed circuit is the opposite value. That is, for example, if the open circuit has a value of “1” then the closed circuit has a value of “0”, and vice versa. The process of breaking the circuit can be performed by, for example, vaporizing, melting, burning, blowing, rupturing, physically modifying, or otherwise disrupting the flow of current through the particular circuit. Each of the breakable devices can operate by receiving an electrical current that causes the creation of the open circuit (e.g., an overcurrent, an excessive load).

The PMIC 125 can effectuate operation directly. In some embodiments, the PMIC 125 can include logic that reads the number of breakable devices and their current state. In some embodiments, the logic is not included in the PMIC 125. For example, the logic can be located within a computer housing the PMIC 125. In another example, the logic can be in a second integrated circuit and can be communicatively coupled to the PMIC 125 through logical traces of a circuit board or through a communication cable or other wire. In some embodiments, the PMIC 125 can apply a current directly to the breakable device. In some embodiments, the PMIC 125 can apply a current indirectly to a breakable device and applying a second current directly to the breakable device. In a first example, a first current is applied to a wire adjacent to a plurality of breakable devices causing the breakable devices to increase in temperature (e.g., heating). After heating, a second current is applied directly to one or more of the plurality of breakable devices causing one or more breakable devices to break, and consequently, creating one or more permanently open circuits. In some embodiments the current applied to the breakable devices in the PMIC 125 to cause the break is provided by an outside source. In this embodiment, the PMIC 125 does not have the internal ability to break any of the breakable devices. In this way the pattern of the breakable devices cannot easily be changed once the encryption module 120 is programmed.

The encryption key burner 127 is a component of the first device 110 that burns in the encryption key into the encryption module 120. The encryption key is burned into the encryption module 120 using the PMIC 125 portions of the encryption module 120. The encryption key value is converted to a binary value. This binary value is then burned in by changing the broken/unbroken status of a number of the PMIC 125 such that the corresponding value represents the encryption key value. For example, if the encryption key value is “6EB957008E03CE4” is converted to a 64-bit binary value of:

 00000110 11101011 10010101 01110000 00001000 11100000 00111100 11100100

To burn this value into the encryption module 120, the encryption module 120 needs to have to have at least 64 PMICs 125 available. The encryption key burner 127 then, depending on the method used for determining a “0” or a “1”, burns the corresponding circuit to either open the circuit or close the circuit. However, the encryption module 120 can have any number of PMICs 125 such that not all of the available PMICs 125 are used for the encryption key. Further, the encryption key value can be any number of bits. However, the encryption module 120 should have at least the number of PMICs 125 as the number of bits in the encryption key. Further, if the first device 110 is to be paired with other devices additional PMICs 125 will be required to store the corresponding encryption keys for the additional devices.

The decryption module 130 is a component of the second device 160 that is configured to decrypt data received from the first device 110 that has been encrypted. The decryption module 130 applies the decryption key to the received data to decrypt the data. The process of decryption can be done using any method for decrypting data. Once the data has been decrypted by the decryption module 130, it can be viewed or otherwise used on the second device 160. In the instance, where the first device 110 controls actions on the second device 160, the decryption of the data permits the second device 160 to modify itself according to the instructions contained in the data.

The decryption key burner 137 is a component of the first device 110 that burns in the decryption key into the decryption module 130. The decryption key is burned into the decryption module 130 using the PMIC 135 portions of the decryption module 130. The decryption key value is converted to a binary value. This binary value is then burned in by changing the broken/unbroken status of a number of the PMIC 135 such that the corresponding value represents the decryption key value. For example, if the decryption key value is “6EB957008E03CE4” is converted to a 64-bit binary value of:

00000110 11101011 10010101 01110000 00001000 11100000 00111100 11100100

While the present description illustrates the same key value used for the encryption key and the decryption key, it should be recognized that in asymmetrical encryption the encryption key and the decryption key do not share the same value.

To burn this value into the decryption module 130, the decryption module 130 needs to have to have at least 64 PMICs 135 available. The decryption key burner 137 then, depending on the method used for determining a “0” or a “1”, burns the corresponding circuit to either open the circuit or close the circuit. However, the encryption module 120 can have any number of PMICs 135 such that not all of the available PMICs 135 are used for the decryption key. Further, the decryption key value can be any number of bits. However, the decryption module 130 should have at least the number of PMICs 135 as the number of bits in the decryption key. Further, if the first device 110 is to be paired with other devices additional PMICs 135 will be required to store the corresponding decryption keys for the additional devices.

The communications module 140 is a component of the first device 110 and the second device 160 that permits the first device 110 and the second device 160 to communicate with each other. The communications module 140 can use any technology or approach to transmit or receive data. In some embodiments the communications module 140 is a transceiver. However, in other embodiments, the communications module 140 can employ network communications technologies, such as ethernet, Wi-Fi, cellular technologies (e.g. GSM, CDMA, LTE, 3G, 4G, 5G, etc.), etc. The communications module 140 transmits and/or receives the encrypted data that is generated by either the first device 110 or the second device 160, respectively.

FIG. 2 is a flow diagram illustrating a process for creating a secure pairing between two or more devices according to embodiments. The process begins when a user or other individual selects the first two devices to be paired with each other. This is illustrated at step 210. Once the devices have been selected, an encryption key is selected for the first device 110. In some embodiments the encryption key can be any type of encryption key including symmetric and asymmetric cryptology.

Once the encryption key has been selected the system proceeds to write the encryption key to the first device 110. This illustrated at step 220. To write the encryption key to the first device 110, the encryption key burner 127 receives the encryption key value and then determines what PMICs 125 of the first device 110 need to be broken. In this way the encryption key burner 127 determines which PMICs 125 should have their corresponding value changed. Depending on how the system determines what a “0” or a “1” is will determine which particular PMICs 125 need to be broken.

After the encryption key has been written to the first device 110, the system proceeds to burn in the encryption key into the PMICs 125. This is illustrated at step 230. To write the encryption key to the first device 110 the encryption key burner 127 breaks the corresponding PMICs 125 such that a corresponding value of “1” or a “0” is created. The process of breaking the circuit can be performed by, for example, vaporizing, melting, burning, blowing, rupturing, physically modifying, or otherwise disrupting the flow of current through the particular circuit. Each of the PMICs 125 can operate by receiving an electrical current that causes the creation of the open circuit (e.g., an overcurrent, an excessive load).

On the second device 160, the system proceeds to write the corresponding decryption key to the second device 160. This illustrated at step 240. To write the decryption key to the first device 110, the decryption key burner 137 receives the encryption key value and then determines what PMICs 135 of the second device 160 need to be broken. In this way the decryption key burner 137 determines which PMICs 135 should have their corresponding value changed. Depending on how the system determines what a “0” or a “1” is will determine which particular PMICs 135 need to be broken.

After the decryption key has been written to the second device 160, the system proceeds to burn in the decryption key into the PMICs 135. This is illustrated at step 250. To write the decryption key to the first device 110 the decryption key burner 137 breaks the corresponding PMICs 135 such that a corresponding value of “1” or a “0” is created. The process of breaking the circuit can be performed by, for example, vaporizing, melting, burning, blowing, rupturing, physically modifying, or otherwise disrupting the flow of current through the particular circuit. Each of the PMICs 135 can operate by receiving an electrical current that causes the creation of the open circuit (e.g., an overcurrent, an excessive load).

The system then proceeds by repeating steps 210-250 on the first device 110 and the second device 160. This is illustrated at step 260. However, instead of writing the encryption key to the first device 110 and the decryption key to the second device 160, the system selects a second encryption key and corresponding second decryption key and writes the second encryption key to the second device 160 and the second decryption key to the first device 110. In some embodiments the second encryption key and second decryption key are different from the encryption key that was written to the first device 110 and the decryption key that was written to the second device 160.

FIG. 3 is a flow diagram illustrating a process for transmitting data from the first device 110 to the second device 160 according to embodiments. It should be noted that the process discussed here with respect to FIG. 3 is equally applicable when the second device 160 transmits data to the first device 110, or any transfer between two devices implementing the encryption/decryption process of the present disclosure. The process begins by the user or an application of the first device 110 initiating a transfer from the first device 110 to the second device 160. This is illustrated at step 310. The initiation of the transfer can occur using the normal processes that the application or user uses to transfer data.

Following the initiation of the data transfer, the data is passed to the encryption module 120 for encryption of the data. This is illustrated at step 320. The encryption module 120 takes the data and encrypts the data according to the process that has been programed into the encryption module 120. To obtain the encryption key to use for the encryption, the encryption module 120 accesses the encryption key that has been burned into the encryption module 120 for transmitting data to the second device 160. If the first device 110 is paired with multiple different devices, the first device 110 can use a table or other identifier to determine which bits in the PMICs 125 represent the encryption key that is to be used to send data to the second device 160. In some embodiments, some of the PMICs 125 can be used to hold an identifier for the encryption key. In this embodiment the encryption module 120 will search the PMICs 125 to find an identifier that indicates that the encryption key is for data to be sent to the second device 160. To enable the ability to find this information, the encryption module 120 can assign each encryption key additional bits to permit the device identifier to be placed before or after the corresponding encryption key. It should be noted that in this embodiment the number of bits assigned to each encryption key and identifier should be the same for all devices. When a device uses a smaller number of bits for its encryption key, the encryption burner can fill in the preceding bits with an indication of “0” to allow the corresponding encryption key to have the “same” number of bits. This allows the module to know that “x” bits represent the key and “y” bits represent the identifier.

Once the data has been encrypted it is transmitted to the second device 160. This is illustrated at step 330. The process of sending the data to the second device 160 can use any method for sending data between two devices. This data is received by the second device 160 who can then proceed the process of decrypting the data. The process of decryption begins when the decryption module 130 obtains the decryption key needed to decrypt the data from the first device 110. This is illustrated at step 340. To obtain the decryption key to use for the decryption, the decryption module 130 accesses the decryption key that has been burned into the decryption module 130 for decrypting data received from the first device 110. If the second device 160 is paired with multiple different devices, the second device 160 can use a table or other identifier to determine which bits in the PMICs 125 represent the decryption key that is to be used to decrypt data received from the first device 110. In some embodiments, some of the PMICs 125 can be used to hold an identifier for the decryption key. In this embodiment the decryption module 130 will search the PMICs 125 to find an identifier that indicates that the decryption key is for data to be received from the second device 160. To enable the ability to find this information, the decryption module 130 can assign each decryption key additional bits to permit a device identifier to be placed before or after the corresponding decryption key. It should be noted that in this embodiment the number of bits assigned to each decryption key and identifier should be the same for all devices. When a device uses a smaller number of bits for its decryption key, the decryption burner can fill in the preceding bits with an indication of “0” to allow the corresponding decryption key to have the “same” number of bits.

To decrypt the data, the data is passed to the decryption module 130, which takes the data and decrypts the data according to the process that has been programed into the decryption module 130. This is illustrated at step 350. Any process for decrypting the data can be used. Once the data is decrypted, the user or application on the second device 160 can use the data to perform whatever action or modification is desired based on the data.

FIG. 4 is a flow diagram illustrating a process for updating or modifying the second device 160 according to embodiments of the present disclosure. After the decryption key is burned into the PMIC the second device 160 is now able to request permission to change or modify features within itself. The approach presented in FIG. 4 allows for one or more devices to exercise control over various actions that can occur on the second device 160. While there are many approaches that allow for one device to control another, such as multi-factor authentication, push notification or biometric validation that require the response to be entered from the controlling device, each of these approaches can be defeated by the user of the second device 160. While defeating this added security can be difficult it is not beyond that of a dedicated individual. For example, parents want to control what applications and features are available on their children’s devices. However, children will often find ways to defeat the parental controls that are placed on their devices. For example, a child could try to jailbreak their device to avoid these controls or could figure out how to override the controls that were placed on the device, by determining the password that was placed on their device to control their device. Similar situations can occur in other environments. For example, companies would like to control what is allowed on their employees’ devices, governments would like to restrict access to certain information or features on their devices or devices that connect to their networks, schools would like to control what websites are viewable from their networks, etc. The present disclosure allows for a more secure controlling of features, access, and modification of a device by a controlling organization.

As discussed above with respect to FIG. 1 the first device 110 and the second device 160 both have a corresponding encryption key and decryption key burned into them using the associated PMICs. These keys allow for the secure transmission of information between the two devices. In this embodiment as discussed above the information that is transmitted between the devices is information related to activity that the second device 160 desires to take and the first device 110 is required to approve of. Because of the nature of this type of communication the encryption module 170 of the second device 160 and the decryption module 130 of the first device 110 is not needed as the request itself does not need to be controlled to the same level as the response. As such in some embodiments these features are not present on the first device 110 and the second device 160. In some embodiments the first device 110 is paired or controls more than one device, and controls each of those devices similarly as is discussed with respect to controlling the second device 160.

Following the pairing of the first device 110 and the second device (step 410) 160 through the encryption/decryption modules 120/180 the second device 160 initiates modifications to become a controlled device. This is illustrated at step 420. These modifications can occur when a command is sent from the first device 110 to the second device 160 instructing the second device 160 to begin these modifications. In some embodiments, the modifications are initiated by a user of the second device 160. For example, by accessing an application (e.g. data processing component 165) on the second device 160 that initiates the modifications. However, in some embodiments, these modifications occur automatically upon the pairing of the two devices. To implement these modifications, the second device 160 includes additional programming or circuitry that prevents the second device 160 from making changes to itself without receiving encrypted confirmation from the first device 110. This programming is activated by the initiated modification. In some embodiments, some of the PMICs that are present in the second device 160 are configured to implement the control feature. For example, some of the PMICs can be gating off circuitry in the second device 160 that when the gate is removed cause the device to become a controlled device. In becoming a controlled device, the second device 160 can implement a preprogrammed second application. This second application implements the controlling features. The application can be a software program operating at the OS level of the second device 160, or can be a program that is implemented at the hardware level of the second device 160, such as through an ASIC.

Once the second device 160 becomes a controlled the device, the user of the second device 160 attempts to modify the second device 160. This is illustrated at step 430. The user can attempt to modify the device in many different ways. For example, the user can attempt to install a new program, make a purchase from an application store, remove a program, activate features on the device, deactivate features on the device, etc. In other instances the modifications can include modifying device settings, firmware, personal information, etc. In other environments the modifications can include controlling what cores can be utilized, what server clusters can be used, etc. Unlike in a normal device, the attempted modifications are not implemented at this time.

The requests to make the modification to the second device 160 is transmitted to the first device 110. This is illustrated at step 440. The request can contain information related to the specific modification that the user desires to make on the second device 160. For example, the user can desire to add a new application to the second device 160. The request then would include information about the specific application the user desires to install. Any information that would be useful to the approver can be included in this information. For example, the name of the application, the cost of the application, a rating of the application, age appropriateness of the application, etc. In some instances, the user can be attempting to access an internet site that is not on a pre-approved list of internet sites. In this instance, the information in the request can include the name of the site to be visited as well as a link to the site. However, any other information can be included about the site, based on information that can be obtained by the programming on the second device 160. This information can also be retrieved by the first device 110. In some instances, the user can be attempting to remove an application from the second device 160. For example, the user can be attempting to remove the approval feature of the second device 160. In this instance the request can include the name of the application or feature the user is attempting to remove. In some embodiments the request is encrypted using the burned in encryption key for additional security in the transaction. However, the encryption of the request is not necessary.

The request for the modification is received at the first device 110. This is illustrated at step 450. If the request is encrypted by the second device 160, the request is decrypted at the first device 110 using the burned in decryption key. The request is then processed and displayed to the holder of the first device 110. This is illustrated at step 460. The request can be processed to show the information contained in the request and that information can be displayed to the holder of the first device 110. In some embodiments, there is an application (e.g., data processing component 105) on the first device 110 that processes the request. The application can use information contained in the request to obtain additional information related to the request. For example, the application can search the internet to find information about the desired change the user wishes to make on the second device 160. This information can then be presented to the holder of the first device 110 to assist them in making a decision as to whether to approve or disapprove of the request. The information can be presented in any number of ways such that the holder can view and digest the information.

The holder of the first device 110 then makes a decision as to approve or disapprove the request. This is illustrated at step 470. In response to the decision of the holder, the application proceeds to have a response prepared and sent to the second device 160. This is illustrated at step 480. The response can be as simple as an indication of the decision made by the holder, or can include additional information and instructions. This information and instructions can include items such as limitations on how the application is to be used. The response is encrypted by the first encryption module 120 and then transmitted to the second device 160. The encryption of the response ensures that the user of the second device 160 cannot intercept the response and modify the response to meet their own desires.

The encrypted response is received at the second device 160, decrypted and implemented. This is illustrated at step 490. The response can be routed to the second application. The second application can receive the response in the encrypted format and then decrypts the response using the burned in decryption key that is present in the decryption module. However, in some embodiments the response is decrypted prior to being provided to the second application. The second application takes the decrypted response and implements its directions. This can include for example permitting the installation of the program, modifying the second device 160 as requested, preventing the installation or modification, etc. By using the pairing process and the encryption/decryption system of the present disclosure, a controlling entity is able to more securely control assets that it desires to control. It ensures that the user of the second device 160 is not able to spoof the response to avoid the controlling features.

Referring now to FIG. 5 , shown is a high-level block diagram of an example computer system 501 that may be used in implementing one or more of the methods, tools, and modules, and any related functions, described herein (e.g., using one or more processor circuits or computer processors of the computer), in accordance with embodiments of the present disclosure. In some embodiments, the major components of the computer system 501 may comprise one or more CPUs 502, a memory subsystem 504, a terminal interface 512, a storage interface 516, an I/O (Input/Output) device interface 514, and a network interface 518, all of which may be communicatively coupled, directly or indirectly, for inter-component communication via a memory bus 503, an I/O bus 508, and an I/O bus interface unit 510.

The computer system 501 may contain one or more general-purpose programmable central processing units (CPUs) 502-1, 502-2, 502-3, and 502-N, herein generically referred to as the CPU 502. In some embodiments, the computer system 501 may contain multiple processors typical of a relatively large system; however, in other embodiments the computer system 501 may alternatively be a single CPU system. Each CPU 502 may execute instructions stored in the memory subsystem 504 and may include one or more levels of on-board cache.

System memory 504 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 522 or cache memory 524. Computer system 501 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 526 can be provided for reading from and writing to a non-removable, non-volatile magnetic media, such as a “hard drive.” Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), or an optical disk drive for reading from or writing to a removable, non-volatile optical disc such as a CD-ROM, DVD-ROM or other optical media can be provided. In addition, memory 504 can include flash memory, e.g., a flash memory stick drive or a flash drive. Memory devices can be connected to memory bus 503 by one or more data media interfaces. The memory 504 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of various embodiments.

Although the memory bus 503 is shown in FIG. 5 as a single bus structure providing a direct communication path among the CPUs 502, the memory subsystem 504, and the I/O bus interface 510, the memory bus 503 may, in some embodiments, include multiple different buses or communication paths, which may be arranged in any of various forms, such as point-to-point links in hierarchical, star or web configurations, multiple hierarchical buses, parallel and redundant paths, or any other appropriate type of configuration. Furthermore, while the I/O bus interface 510 and the I/O bus 508 are shown as single respective units, the computer system 501 may, in some embodiments, contain multiple I/O bus interface units 510, multiple I/O buses 508, or both. Further, while multiple I/O interface units are shown, which separate the I/O bus 508 from various communications paths running to the various I/O devices, in other embodiments some or all of the I/O devices may be connected directly to one or more system I/O buses.

In some embodiments, the computer system 501 may be a multi-user mainframe computer system, a single-user system, or a server computer or similar device that has little or no direct user interface, but receives requests from other computer systems (clients). Further, in some embodiments, the computer system 501 may be implemented as a desktop computer, portable computer, laptop or notebook computer, tablet computer, pocket computer, telephone, smart phone, network switches or routers, or any other appropriate type of electronic device.

It is noted that FIG. 5 is intended to depict the representative major components of an exemplary computer system 501. In some embodiments, however, individual components may have greater or lesser complexity than as represented in FIG. 5 , components other than or in addition to those shown in FIG. 5 may be present, and the number, type, and configuration of such components may vary.

One or more programs/utilities 528, each having at least one set of program modules 530 may be stored in memory 504. The programs/utilities 528 may include a hypervisor (also referred to as a virtual machine monitor), one or more operating systems, one or more application programs, other program modules, and program data. Each of the operating systems, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Programs 528 and/or program modules 503 generally perform the functions or methodologies of various embodiments.

The present invention may be a system, a method, and/or a computer program product at any possible technical detail level of integration. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user’s computer, partly on the user’s computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user’s computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The descriptions of the various embodiments of the present disclosure have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. 

What is claimed is:
 1. A method of controlling a device, comprising attempting to modify a second device; generating a request to a first device, the request indicating the attempted modification; transmitting the request to the first device; receiving the request at the first device; determining a response to the request at the first device; encrypting the response at the first device; transmitting the encrypted response to the second device; decrypting the encrypted response at the second device; and implementing the response by the second device.
 2. The method of claim 1 further comprising: writing an encryption key to the first device; burning the encryption key into an encryption module on the first device; writing a corresponding decryption key to the second device, the decryption key allowing the second device to decrypt data transmitted by the first device; and burning the decryption key into a decryption module on the second device.
 3. The method of claim 2 wherein the decryption key is burned into a plurality of physically modifiable internal components (PMIC) disposed on the decryption module, wherein each of the plurality of PMICs can only be modified one time.
 4. The method of claim 3 wherein the decryption key is burned into the plurality of PMICs as a binary representation of the decryption key.
 5. The method of claim 2 wherein the encryption key and decryption key are a private key pair.
 6. The method of claim 1 wherein attempting to modify the second device comprises: attempting to add a new application to the second device.
 7. The method of claim 1 wherein attempting to modify the second device comprises: attempting to access a remote site.
 8. The method of claim 1 wherein the response is a positive response, wherein implementing further comprises: allowing the attempt to modify the second device to proceed.
 9. The method of claim 1 wherein the response is a negative response, wherein implementing further comprises: blocking the attempt to modify the second device from proceeding.
 10. The method of claim 1 wherein receiving the response further comprises: identifying information in the request that indicates a specific modification that a user is attempting to make to the second device.
 11. The method of claim 10 wherein the information includes external information about the specific modification.
 12. The method of claim 1 further comprising: pairing the second device to the first device.
 13. The method of claim 1 further comprising: encrypting the request at the second device; and decrypting the request at the first device.
 14. The method of claim 13 wherein the encryption key is burned into a plurality of physically modifiable internal components (PMIC) disposed on the encryption module, wherein each of the plurality of PMICs can only be modified one time.
 15. The method of claim 14 wherein the encryption key is burned into the plurality of PMICs as a binary representation of the encryption key.
 16. A system for providing secure data transfer between two devices, comprising: a first device, comprising: an encryption module configured to encrypt data prior to transmission to a second device using an encryption key; an encryption burner configured to burn the encryption key into the encryption module; a data processing component configured to respond to a request from the second device to modify the second device, wherein a response is sent to the second device encrypted by the encryption module; the second device, comprising: a decryption module configured to decrypt data received from the first device using a decryption key; a decryption burner configured to burn the decryption key into the decryption module; a second data processing component configured to generate the request to modify the second device, to receive the response from the first device, and implement the response on the second device; and wherein the encryption key and decryption key are a public/private key pair.
 17. The system of claim 16 wherein the decryption key is burned into a plurality of physically modifiable internal components (PMIC) disposed on the decryption module, wherein each of the plurality of PMICs can only be modified one time.
 18. The system of claim 17 wherein the decryption key is burned into the plurality of PMICs as a binary representation of the decryption key.
 19. The system of claim 16 wherein the response is either a positive response indicating that the modification can take place, or a negative response indicating that the modification cannot take place.
 20. The system of claim 19 wherein the second data processing component is configured to not permit modification of the second device in the absence of the positive response. 